The CLI decomposition moved update prompt logic into src/toolchain and thinned the bin entrypoint, but the status tests still inspected the old bin source and scan/doctor still treated removed workflow shims as required managed files. That made the zero-copy install surface look broken after setup even though the intended assets were present.

This points the prompt-source assertions at src/toolchain and narrows the required managed file list to the assets that setup still installs, so status/doctor align with the zero-copy contract instead of demanding legacy repo shims.

Constraint: Zero-copy setup intentionally removes legacy workflow shims from managed repo installs
Rejected: Reinstall deleted workflow shims during setup | would regress the CLI-owned install surface
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep REQUIRED_MANAGED_REPO_FILES aligned with setup/doctor zero-copy expectations when moving assets between bin and src
Tested: node --test test/status.test.js test/metadata.test.js
Tested: node --test --test-name-pattern "setup provisions workflow files and repo config|doctor repairs setup drift and confirms repo is safe" test/setup.test.js test/doctor.test.js
Not-tested: full repo test suite